Skip to content

Getting ready for release v8.5.0 - #383

Open
gr5 wants to merge 5 commits into
masterfrom
new_release
Open

gr5 wants to merge 5 commits into
masterfrom
new_release

Conversation

@gr5

@gr5 gr5 commented Aug 26, 2026 •

Copy link
Copy Markdown
Collaborator

This may be a bit early but I'm getting ready for the next release. I'm hoping at least one more pr (zernike checkboxes) will be merged first.

#366

@github-actions

Copy link
Copy Markdown

🚀 New build available for commit b07def7
Download installer here

@atsju atsju left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Version 2.1 is duplicated at bottom of document. Please fix it too.

Line 223 there is a trailing \ that has nothing to do there

Comment thread RevisionHistory.html Outdated
Comment thread RevisionHistory.html
Comment thread RevisionHistory.html Outdated
Comment thread RevisionHistory.html Outdated
gr5 and others added 4 commits August 27, 2026 12:36
Co-authored-by: Julien Staub <atsju2@yahoo.fr>
Co-authored-by: Julien Staub <atsju2@yahoo.fr>
Co-authored-by: Julien Staub <atsju2@yahoo.fr>
Optimistically added live video mode feature
removed a backslash
section 2.1 was duplicated
@gr5

gr5 commented Aug 27, 2026

Copy link
Copy Markdown
Collaborator Author

I fixed the backslash and the duplicate section 2.1.

I also optimistically added the live video feature. 😄 I can always remove that if it doesn't get merged in.

@github-actions

Copy link
Copy Markdown

🚀 New build available for commit be499be
Download installer here

@github-actions

Copy link
Copy Markdown

🚀 New build available for commit dc3e6ef
Download installer here

@github-actions

Copy link
Copy Markdown

🚀 New build available for commit b0beb22
Download installer here

@github-actions

Copy link
Copy Markdown

🚀 New build available for commit e93e239
Download installer here

@atsju
atsju self-requested a review August 27, 2026 17:08
@atsju

atsju commented Aug 27, 2026

Copy link
Copy Markdown
Collaborator

I approve this. I would let it open until you are really ready to do the release.
There is no hurry to merge.

@atsju

atsju commented Aug 27, 2026

Copy link
Copy Markdown
Collaborator

@Lucassifoni I believe there is a real causes for the build failure on Mac.

@gr5

gr5 commented Aug 27, 2026

Copy link
Copy Markdown
Collaborator Author

Yeah, probably a real error. Strange that it didn't do it one time.

Can you look into it? I don't understand the build stuff.

@Lucassifoni

Copy link
Copy Markdown
Contributor

@Lucassifoni I believe there is a real causes for the build failure on Mac.

On it !

@Lucassifoni

Copy link
Copy Markdown
Contributor

Okay, the versions of libraries pulled by homebrew in the arm64 and intel github actions runners differ, but that shouldn't be blocking. The checks in the workflow are too strict. The actual build are fine but their combination logic in an universal DMG is too strict right now. Opening a PR.

@Lucassifoni

Copy link
Copy Markdown
Contributor

Hello,
This last month back to work has been having me fully unavailable. Am I blocking the 8.5.0 release ? Do you need something specific from me ? Don't hesitate to ping me, it calmed down a bit and I have time again on weekends.

@gr5

gr5 commented Oct 3, 2026

Copy link
Copy Markdown
Collaborator Author

As far as I know you are not blocking anything. yet.

I wanted to get Dale's latest "live video" feature into 8.5. It is basically ready but Dale keeps tweaking it. Which is great. It's on branch blinkrate. Dale is doing 99% of the developing and we are emailing each other multiple times per day. I've been doing a lot of testing of his features.

We did get an error in the "universal-dmg" part of the build. And blinkrate has latest master merged into it. So that's not good. I haven't looked at that at all as I don't know much about yaml or mac.

@Lucassifoni

Copy link
Copy Markdown
Contributor

Oh, I see it. I’ll be on it tonight. If it continues happening in future releases I’d advise staying on two separate architectures for Mac until I get more experience with the lipo’d build to avoid blocking future releases. But I’ll work on it first.

@gr5

gr5 commented Oct 3, 2026

Copy link
Copy Markdown
Collaborator Author

thanks. I don't think we'll need that fixed for at least a few days. Even if Dale declares he is done today, I promised I would add a camera exposure feature. Plus I need to change something that Julien did recently. I keep thinking we are less than a week away and then Dale comes out with some completely new feature related to video capture.

@Lucassifoni

Copy link
Copy Markdown
Contributor

Actually the blinkrate branch is 18 commits behind master, including the #384 fixes. I think getting it in sync with master will fix the universal DMG diffing step.

@gr5

gr5 commented Oct 3, 2026

Copy link
Copy Markdown
Collaborator Author

oh! User error! I did this command (never tried it before):
git merge-base master blinkrate

And it gave me the correct merge base of the two and when I searched for that commit it was shown as the latest branch but I guess I must have searched only on blinkrate branch or maybe I didn't do a git fetch. Not sure. Either way I screwed up. I can see now that we need to merge master into blinkrate again. Sorry to cause you unnecessary work.

@githubdoe

Copy link
Copy Markdown
Owner

I get a bit lost here. I merged with master a week or so ago. So how can we be behind even if George did something wrong. Does that mean that blinkrate somehow reverted to before my merge and now I when I merged George's code it is behind. OR can I just push my current changes and be back up to current.

@gr5

gr5 commented Oct 4, 2026

Copy link
Copy Markdown
Collaborator Author

git keeps records of everything. You did the merge on 8/25. It might seems like just a week or two ago but it was a little over a month ago.

There were some changes to master between 8/25 and 9/3 and nothing since then. So nothing in a month but a few changes after 8/25.

It would be good to merge master into blinkrate soon.

I just did a quick test merge (just a practice to see what would happen if I merged). Google to learn how to do this yourself if you want. Anyway there are conflicts in only 2 files: wavefront.h and wavefront.cpp. Some changes related to the whole discussion of deep copy versus shallow copy and copy constructors and such as it relates to class wavefront. That's in wavefront.cpp

And something else that affects 2 lines of code in wavefront.h. I think maybe something got moved around in the .h file possibly and merge got confused. I'd have to look at the entire .h file, not just the affected spot.

@githubdoe

githubdoe commented Oct 4, 2026 via email

Copy link
Copy Markdown
Owner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants